翻訳と辞書
Words near each other
・ Hardy Nickerson
・ Hardy Nilsson
・ Hardy Oil and Gas
・ Hardy Pace
・ Hardy Peninsula
・ Hardy Perennials and Old Fashioned Flowers
・ Hardy Place, California
・ Hardy Plant Society
・ Hardy Point
・ Hardy Pond
・ Hardy Powers
・ Hardware verification language
・ Hardware virtualization
・ Hardware Wars
・ Hardware, Virginia
Hardware-assisted virtualization
・ Hardware-based full disk encryption
・ Hardware-dependent software
・ Hardware-in-the-loop simulation
・ Hardwarehouse
・ HardwareZone
・ Hardwasser (Wiera)
・ Hardway
・ Hardway, Hampshire
・ Hardwell
・ Hardwell Castle
・ Hardwell discography
・ Hardwell On Air
・ Hardwell presents 'Revealed Volume 4'
・ Hardwick


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Hardware-assisted virtualization : ウィキペディア英語版
Hardware-assisted virtualization

In computing, hardware-assisted virtualization is a platform virtualization approach that enables efficient full virtualization using help from hardware capabilities, primarily from the host processors. Full virtualization is used to simulate a complete hardware environment, or virtual machine, in which an unmodified guest operating system (using the same instruction set as the host machine) executes in complete isolation. Hardware-assisted virtualization was added to x86 processors (Intel VT-x or AMD-V) in 2006.
Hardware-assisted virtualization is also known as accelerated virtualization; Xen calls it hardware virtual machine (HVM), and Virtual Iron calls it native virtualization.
== History ==

Hardware-assisted virtualization first appeared on the IBM System/370 in 1972, for use with VM/370, the first virtual-machine operating system. With the increasing demand for high-definition computer graphics (e.g. CAD), virtualization of mainframes lost some attention in the late 1970s, when the upcoming minicomputers fostered resource allocation through distributed computing, encompassing the commoditization of microcomputers.
IBM offer hardware virtualization for their POWER CPUs under AIX (e.g. System p) and for their IBM-Mainframes System z. IBM refers to their specific form of hardware virtualization as "logical partition", or more commonly as LPAR.
The increase in compute capacity per x86 server and in particular the substantial increase in modern networks' bandwidths rekindled interest in data-center based computing which is based on virtualization techniques. The primary driver was the potential for server consolidation: virtualization allowed a single server to cost-efficiently consolidate compute power on multiple underutilized dedicated servers.
Cloud computing as the new synonym for the said data center based computing (or mainframe-like computing, respectively) through high bandwidth networks is the most visible hallmark of a return to the roots of computing. It is closely connected to virtualization.
The initial implementation x86 architecture did not meet the Popek and Goldberg virtualization requirements to achieve "classical virtualization":
* equivalence: a program running under the virtual machine monitor (VMM) should exhibit a behavior essentially identical to that demonstrated when running on an equivalent machine directly
* resource control (also called safety): the VMM must be in complete control of the virtualized resources
* efficiency: a statistically dominant fraction of machine instructions must be executed without VMM intervention
This made it difficult to implement a virtual machine monitor for this type of processor. Specific limitations included the inability to trap on some privileged instructions.〔

To compensate for these architectural limitations, designers have accomplished virtualization of the x86 architecture through two methods: full virtualization or paravirtualization.〔Chris Barclay, ''New approach to virtualizing x86s'', Network World, 10/20/2006〕 Both create the illusion of physical hardware to achieve the goal of operating system independence from the hardware but present some trade-offs in performance and complexity.
# Paravirtualization is a technique in which the hypervisor provides an API and the OS of the guest virtual machine calls that API, requiring OS modifications.
# Full virtualization was implemented in first-generation x86 VMMs. It relies on binary translation to trap and virtualize the execution of certain sensitive, non-virtualizable instructions. With this approach, critical instructions are discovered (statically or dynamically at run-time) and replaced with traps into the VMM to be emulated in software. Binary translation can incur a large performance overhead in comparison to a virtual machine running on natively virtualized architectures such as the IBM System/370. VirtualBox, VMware Workstation (for 32-bit guests only), and Microsoft Virtual PC, are well-known commercial implementations of full virtualization.
In 2005 and 2006, Intel and AMD (working independently) created new processor extensions to the x86 architecture called Intel VT-x and AMD-V, respectively (On the Itanium architecture, hardware-assisted virtualization is known as VT-i). The first generation of x86 processors to support these extensions were released in late 2005 early 2006:
*On November 13, 2005, Intel released two models of Pentium 4 (Model 662 and 672) as the first Intel processors to support VT-x.
*On May 23, 2006, AMD released the Athlon 64 ("Orleans"), the Athlon 64 X2 ("Windsor") and the Athlon 64 FX ("Windsor") as the first AMD processors to support this technology.
Well-known implementations of hardware-assisted x86 virtualization include VMware Workstation (for 64-bit guests only), Xen 3.x (including derivatives like Virtual Iron), Linux KVM and Microsoft Hyper-V.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Hardware-assisted virtualization」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.